Specify what presence of an image means - #1260
Conversation
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
|
Note: This has to be debated in SIG Std/Cert, particularly the case of |
|
@mbuechse Could you please elaborate/confirm that this change only aligns the canonical texts with the existing compliance checks. Since I see no diff in |
|
Visibility of community < public. Fine for me the add this. I don't like the public visibility and prefer community over public. |
|
@toothstone I can confirm that: standards/Tests/iaas/openstack_test.py Line 66 in 514377b However, in my mind, it's more important that the standard makes sense. This is v2, which is still a draft, so we can and should discuss in the SIG what makes most sense. |
|
Is something else to do here based on the discussion in the SIG on 2026-08-06 or can this be merged? |
garloff
left a comment
garloff
left a comment
There was a problem hiding this comment.
From my perspective, this is good to go.
- Operators can provide images as public (preferrable) or as community images.
- Only those are considered by the standard.
- This means that creating a customer-specific image (private) or one that is shared from one customer to another are neither subject to these rules nor can they be used to fulfill the mandatory list ...
There is a separate discussion on filtering out snapshots.
5 participants
No description provided.